Getting the Saliency Toolkit
Most importantly, mbarivision requires the Saliency Toolkit from the ilab at USC. The Saliency toolkit is distributed as source files, so you must compile it. To get the Toolkit, you must ask for permission to use it by following the instructions on the bottom of this page: http://ilab.usc.edu/toolkit/downloads.shtml. Let them know you will be using this with the AVED software from MBARI. As long are you are using the Toolkit for academic or research use, you will be granted access to the code. You will be emailed a user login and password to check out the code from the ilab SVN repository. If you don't have Subversion installed, you can install it using:
yum install subversion
Once you get the password to the iLab repository, check-out the saliency code from the date 2008-04-15 using svn. Important - we unfortunately are working with an older version of the toolkit because we haven't had time to port our code to work with the latest saliency revision. So, to be compatible with the version we are working with, you must checkout the release on the date 2008-04-15. The checkout command:
svn checkout --username anonsvn svn://iLab.usc.edu/trunk/saliency --revision {2008-04-15} saliency
Requirements for building the Saliency Toolkit
Next, install the Saliency Toolkit library dependencies using yum if needed. These are the dependencies we have found from our last experience installing it on Fedora Core 9 that may be needed. These may already be installed on your system, but it's always a good idea to check first:
| Library | RPM Packages | Fedora command |
|---|---|---|
| libX11 | xorg-x11-proto-devel |
yum -y install xorg-x11-proto-devel |
| gcc |
gcc-c++ | yum -y install gcc-c++ |
| tclsh |
tclx |
yum -y install tclx |
| libXShm-devel |
libXext-devel |
yum -y install libXext-devel |
| libbz2-devel | bzip2-devel |
yum -y install bzip2-devel |
| libz-devel |
zlib-devel | yum -y install zlib-devel |
| libxml2-devel |
xml2-devel | yum -y install xml2-devel |
| lpng |
libpng and libpng-devel |
yum -y install libpng libpng-devel |
| ljpeg |
libjpeg and libjpeg-devel |
yum -y install libjpeg libjpeg-devel |
| libavcodec, libavutil, libavformat |
ffmpeg and ffmpeg-devel or install from sources (see below) |
You will also need the gcc compiler version gcc-3.4.X. We suggest 3.4.3. If you are running a more recent version e.g. gcc-4.3 it will not compile correctly.
Download gcc from here:
http://ftp.gnu.org/gnu/gcc/gcc-3.4.3/
This is a good site to orient you on how to install a second gcc compiler:
http://www.faqs.org/docs/ldev/0130091154_71.htm
When the new compiler is installed, you can use this new compiler in the saliency build by setting the following environment variables to point to your gcc-3.4.3 version before running configure.
| Environment Variable | Description |
|---|---|
| CC | C compiler command |
| LDFLAGS | linker flags, e.g. -L<lib dir> if you have libraries in a nonstandard directory <lib dir> |
| CPPFLAGS | C/C++/Objective C preprocessor flags, e.g. -I<include dir> if you have headers in a nonstandard directory <include dir> |
| CXX | C++ compiler command |
Building ffmpeg from source
If you cannot get ffmpeg in a RPM, to install ffmpeg from sources, get the last version. Checkout ffmpeg, build, and install (this assumes you have sudo permissions to install applications to /usr):
svn checkout svn://svn.mplayerhq.hu/ffmpeg/trunk ffmpeg cd <path-to-ffmpeg> ./configure --enable-shared --prefix=/usr make sudo make install
Building the Saliency Toolkit
When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make core and tprogs build rules with the following command:
cd <path-to-saliency> ./configure --without-qtdir --enable-force32 make core make tprogs
 | Warning Don't change these configuration options or it will break the AVED mbarivision build. You can add options like --prefix, --enable-quitecompile, etc. but don't remove the options above. If you want to experiment with the saliency toolkit, copy it to a separate directory that won't be used in the AVED mbarivision build ! |
Now, go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to Step 2. Build and Install XML Libraries
